home *** CD-ROM | disk | FTP | other *** search
- okay, i'm having a lot of trouble getting winsock to work on my pc at
- home, running slip.
-
- first off, does trumpet winsock work over Netcom's SLIP server? (those
- who are on netcom and use trumpet winsock can help me out here.)
-
- secondly, this is my setup: an internal 14.4 Digicom Scout Plus modem,
- on COM2. i've tried various slip drivers (umslip, slipper, cslipper)
- and they don't seem to work. anyway, here's what i did:
-
- 1. loaded the slip driver (umslip, slipper com2 vec=0x60 baud=14400
- (when i typed this i got "16550 found - using FIFO").
-
- 2. loaded the WINPKT driver "winpkt 0x60". it said "Packet driver found at
- 131E/Using old vector 0x60.
-
- 3. fired up windows and started tcpman. i left the default settings
- (my tcpman.ini follows:)
-
- [Trumpet Winsock]
- ip = 192.187.167.44
- netmask = 0.0.0.0
- gateway = 0.0.0.0
- dns = 192.100.81.101 192.100.81.105
- time =
- domain = netcom.com
- vector = 00
- mtu = 1500
- rwin = 4096
- mss = 1460
- slip-enabled = 1
- slip-port = 2
- slip-baudrate = 14400
- slip-handshake = 1
- slip-compressed = 1
-
- however, when i try to use the automatic dialer, it freezes and i must
- press ESC to abort. the dialer does not work. i think it does work
- if the slip driver is not installed.
-
- therefore i tried using my comm program to start a session and then
- quit with the connection still active. however, this doesn't work
- either, when i try running winsock apps, i get "can't resolve
- hostname" type errors, and in the TCPMAN window i get a
- WSAENOTSOCK(number) error.
-
- i'm confused. do i need to dial up the slip server before i load my
- SLIP driver? am i using the wrong slip driver? am i missing
- something? please help, i would really like to get Trumpet winsock
- going; i have it working just fine at my job.
-
- thank you very much,
-
- malcolm
- --
- Malcolm D. Moore * BioData MIS * malcolm@biodata.com * mdm2@netcom.com
- "from city to city, valley to valley, ain't any other state on hit like Cali!"
- "well damn, Short, if it wasn't for earthquakes, rampant crime
- and a lifeless economy, i'd agree witcha." - me
- From news@bigblue.oit.unc.edu Sat Mar 26 17:15:03 1994
- Received: from bigblue.oit.unc.edu by SunSITE.Unc.EDU (5.65c+IDA/FvK-1.07) with SMTP
- id AA28330; Sun, 27 Mar 1994 11:11:55 -0500
- Received: by bigblue.oit.unc.edu (AIX 3.2/UCB 5.64/4.03)
- id AA23133; Sun, 27 Mar 1994 10:47:57 -0500
- Received: from GATEWAY by bigblue with netnews
- for winsock@sunsite.unc.edu (winsock@sunsite.unc.edu)
- To: winsock@sunsite.unc.edu
- Date: 27 Mar 1994 01:15:03 -0800
- From: csdi@nic.cerf.net (Michael Williams)
- Message-Id: <2n3iqn$g4t@nic.cerf.net>
- Organization: CERFnet Dial n' CERF Customer
- Sender: ses
- References: <glenho.9.2D8CDE76@wimsey.com>
- Subject: Re: Net Manage's Chameleon
-
- Glen Houghton (glenho@wimsey.com) wrote:
- : Has anyone used the TCP/IP product they offer ? I would like to use it to
- : connect to my NTAS machine at work to my Windows workstation as a remote
- : adminstrator console much like Rconsole in Novell. Any suggestions?
-
- : Regards
- : Glen Houghton
-
-
- The Microsoft Remote Access Service (RAS) is a better way to go if you
- want to do remote administration. Currently, TCP/IP support for
- Windows NT/AS is a little weak. This is supposed to be improving
- soon but right now I don't think that there is a telnet daemon that
- runs on the NT server that can accept you logon over IP. You
- can connect to the server over IP but you will have problems
- at the application level.
-
- Good luck.
-
- Michael Williams
- California System Design, Inc.
-
-
-